Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1809

reference: 272-tree-1
name: 1809
tree-preservation-order: undefined
272-tpo-1
uprn
address-text
point: POINT (-0.979263 50.858590)
geometry: MULTIPOLYGON (((-0.979164 50.858580,-0.979168 50.858599,-0.979182 50.858617,-0.979204 50.858631,-0.979231 50.858640,-0.979262 50.858644,-0.979293 50.858641,-0.979321 50.858632,-0.979343 50.858618,-0.979357 50.858601,-0.979363 50.858582,-0.979358 50.858562,-0.979345 50.858544,-0.979323 50.858530,-0.979295 50.858521,-0.979265 50.858518,-0.979234 50.858521,-0.979206 50.858529,-0.979184 50.858543,-0.979169 50.858560,-0.979164 50.858580)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL